CALL FOR TOOL DEMONSTRATIONS
Third International Conference on
Generative Programming and Component Engineering (GPCE'04)
Vancouver, October 24-28, 2004
co-located with OOPSLA 2004
and ISMM 2004
Sponsored by ACM SIGPLAN,
in cooperation with ACM SIGSOFT and Microsoft
http://gpce04.gpce.org
Demonstrations Committee
- Simon Helsen (Chair), University of Waterloo, Canada
- William Cook, University of Texas at Austin, USA
- Frédéric Jouault, Université de Nantes, France
Important Dates
- Demonstration proposal submission: July 2, 2004
- Notification of acceptance: August 2, 2004
- Conference: October 24-28, 2004
Overview
The conference on Generative Programming and Component Engineering
offers practitioners and tool-developers an opportunity to give an
in-depth technical demonstration of products, tools, techniques or
approaches supporting program generation, domain-specific modeling,
generative programming, template meta-programming,
aspect-oriented software development, model-driven architecture,
component generation, and other related topics.
GPCE tool demonstrations typically show how tools are applied in real
world scenarios, for example, by considering a small case-study. We
explicitely invite proposals from both industry as well as academia.
Demonstrations will be selected on their technical content, practical
or academic relevance, and feasibility of the proposed demonstration.
While we encourage proposals for the demonstration of commercial
tools, we expect the presentation to address technical issues.
Product marketing is inappropriate for this forum. If there are
concerns with regard to the applicability of a demonstration or tool,
feel free to contact the demonstrations chair (
demos04@gpce.org).
OOPSLA 2004 Co-location
Because GPCE 2004 is co-located with OOPSLA 2004 and because there is
possibly some conceptual overlap, GPCE demonstrations will
be held together with OOPSLA demonstrations. In practice, this means
that GPCE demonstrations will run as a parallel track next to OOPSLA
demonstrations in the same exhibition space. We expect that this integration
benefits both GPCE and OOPSLA conference attendants.
Organizational Issues
A demonstration session will be 45 minutes in length and will be held twice
over the course of the conference. It is centered
around a technical exposition of the tool, but the demonstrators
should provide time for questions from the public, either
during the session or at the end. Depending on resource availability,
there will be time and room for additional informal presentations and
discussions.
Demonstration proposals, written according to the guidelines
outlined below, should be sent by e-mail to the demonstrations chair
(
demos04@gpce.org). The deadline
for proposals is July 2, 2004. Due to the OOPSLA co-location,
the GPCE and OOPSLA demonstrations chairs reserve the right to transfer
incoming proposals between the two conferences whenever appropriate.
Presenters of accepted demonstrations will also be expected to provide a
two-page summary description to be published on the website and handed out
at the conference.
Proposal Guidelines
A proposal for demonstration has to be sent via e-mail to the demonstration chair in
either text, PDF
or MS Word format and should contain the following information:
- A demonstration title
- Name, organization, email, address, and phone number of the contact person
- Names and affiliations of the other presenters
- A description (max 250 words) addressing the following issues:
- Problems addressed
- Relevance to Generative Programming or Component Engineering
- Uniqueness of design and implementation,
- Underlying implementation techniques and technologies used
- A description of what the audience will see and how the
demonstration will be run
- A URL of a web site with additional information, if available
- Hardware and presentation requirements
Proposals may be resent up to the submission deadline (please, indicate clearly
that your proposal is an update of a previous submission).
More Information
For additional information, clarification, or questions, please feel
free to contact the demonstrations chair (
demos04@gpce.org)
Vancouver, October 24-28, 2004
co-located with
OOPSLA 2004
and
ISMM 2004
Sponsored by ACM
SIGPLAN,
in cooperation with ACM
SIGSOFT and Microsoft
http://gpce04.gpce.org
electronic submission at
http://gpce.program-transformation.org
Scope
Generative and component approaches have the potential to revolutionize software development in a similar way as automation and components revolutionized manufacturing. Generative Programming (developing programs that synthesize other programs), Component Engineering (raising the level of modularization and analysis in application design), and Domain-Specific Languages (elevating program specifications to compact domain-specific notations that are easier to write and maintain) are key technologies for automating program development.
GPCE arose as a joint conference, merging the prior conference on Generative and Component-Based Software Engineering (GCSE) and the Workshop on Semantics, Applications, and Implementation of Program Generation (SAIG). The goal of GPCE is to provide a meeting place for researchers and practitioners interested in cutting edge approaches to software development. We aim to foster further cross-fertilization between the software engineering research community on the one hand, and the programming languages community on the other, in addition to supporting the original research goals of both the GCSE and the SAIG communities. We seek papers both in software engineering and in programming languages, and especially those that bridge the gap and are accessible to both communities at the same time.
Topics of Interest
The conference solicits submissions related (but not limited) to:
- Generative programming
- Reuse, meta-programming, partial evaluation, multi-stage and multi-level languages, step-wise refinement
- Semantics, type systems, symbolic computation, linking and explicit substitution, in-lining and macros, templates, program transformation
- Runtime code generation, compilation, active libraries, synthesis from specifications, development methods, generation of non-code artifacts, formal methods, reflection
- Generative techniques for
- Product lines and architectures
- Embedded systems
- Model-driven architecture
- Component-based software engineering
- Reuse, distributed platforms, distributed systems, evolution, analysis and design patterns, development methods, formal methods
- Integration of generative and component-based approaches
- Domain engineering and domain analysis
- Domain-specific languages (DSLs) including visual and UML-based DSLs
- Separation of concerns
- Aspect-oriented programming, feature-oriented programming,
- Intentional programming, and multi-dimensional separation of concerns
- Industrial applications
Reports on applications of these techniques to real-world problems are especially encouraged, as are submissions that relate ideas and concepts from several of these topics, or bridge the gap between theory and practice. The program committee is happy to advise on the appropriateness of a particular subject.
Venue
The conference will be held in Vancouver Trade and Convention Center and Pan Pacific Hotel in Vancouver and will be co-located with
OOPSLA 2004.
Paper Submission
Authors are invited to submit a title and abstract by March 12, 2004, and a full paper by March 19, 2004. These deadlines are firm. Simultaneous submission to other venues and submission of previously published material are not allowed.
Electronic submission will be required, except by special arrangement with the program chairs. Authors will be notified of acceptance by May 17, 2004. Final versions of the papers must be submitted by July 25, 2004.
Accepted papers will appear in the conference proceedings published in the Springer-Verlag Lecture Notes in Computer Science (LNCS) series. (
http://www.springer.de/comp/lncs/index.html).
Submissions must be in PDF, must conform to the LNCS style, and be no longer than
20 pages. For the formatting details see
http://www.springer.de/comp/lncs/authors.html.
Important Dates
Technical papers
- Pre-submission: March 12, 2004 (closed)
- Submission: March 19, 2004 (closed)
- Notification: May 17, 2004 (closed)
- Final version: July 25, 2004 (closed)
Submissions of proposals
- Workshops: March 19, 2004 (closed)
- Tutorials: April 2, 2004 (closed)
- Demonstrations: July 2, 2004 (closed)
Conference
- Tutorials: October 24, 2004
- Workshops: October 25, 2004
- Demonstrations: October 26-28, 2004
- Papers: October 26-28, 2004
Organization
General chair
- Tim Sheard (OGI School of Science & Engineering at OHSU)
Program committee chairs
Program committee
Workshop Chair
Tutorial Chair
- Jeff Gray (University of Alabama at Birmingham)
Demos Chair
Steering Committee
Contact
Vancouver, October 24-28, 2004
co-located with
OOPSLA 2004
and
ISMM 2004
Sponsored by ACM
SIGPLAN,
in cooperation with ACM
SIGSOFT and Microsoft
http://gpce04.gpce.org
Poster Chair
Important Dates
- Poster proposal submission:
- Notification of acceptance:
- Conference:
Overview
Posters at GPCE provide an excellent forum for authors to present their work in an informal and interactive setting. Posters are ideal for presenting speculative, late-breaking results or for giving an introduction to interesting, innovative work. They are intended to provide authors and interested participants with the ability to connect with each other and to engage in discussions about the work. Posters provide authors with a unique opportunity to make their work highly visible during the conference. Therefore, authors of other GPCE technical submissions are encouraged to also submit a poster about their work. Posters will be on display during the entire conference.
Successful posters are carefully designed to convey technical details. They should also have a strong visual impact that attracts the attention of attendees as they stroll past the displays, either during the interactive poster session or at other times during the conference. The goal is to develop a poster that encourages and facilitates small groups of individuals interested in a technical area to gather and interact. The interactive poster session is held early in the conference, to promote continued discussion among interested parties.
Submission Format
The poster itself or the preliminary graphic layout must be submitted as a PDF file. A Poster proposal consists of:
- a 50 word or less short abstract that summarizes the content of the poster
- a set of keywords describing the technical area of the work
- a two-page extended abstract, suitable for inclusion in the GPCE 2004 Conference CD
- the poster itself, or a preliminary graphic layout of the poster (please review the poster content guidelines)
The preliminary graphic layout should consist of 1 to 3 pages that sketch the layout for an ?.?? meter (wide) by ?.?? meter (high) bulletin board. Please use 10 point or larger font in the preliminary layout, and 12 point or larger in the final poster, so that it is readable. Once you have submitted your proposal, you will receive confirmation by e-mail that your proposal has been received and is complete.
Please send poster proposals to the GPCE 2004 Posters Chair TBA to arrive no later than TBA. For additional information, clarifications, questions, or special requirements, please also contact .
Submission Guidelines
Posters cover the same interest areas as the Technical Papers, Demonstrations, and Workshops, and provide an opportunity to present work in a highly visual and interactive format:
- Conference participants who are giving technology demonstrations should consider presenting posters that contain overviews of their demonstrations, both to attract additional attendance at demonstrations and to increase the visibility of their tools.
- Technology providers can showcase their tools and technologies with posters.
- The poster session provides graduate students with an outstanding forum in which to present and discuss their PhD work.
- Research laboratories and projects can introduce themselves and their key efforts to the community by presenting posters.
- Workshop organizers and/or attendees may present posters that summarize results from GPCE 2003 workshops. The poster session provides workshop participants a means of communicating their key results to the rest of the community.
- Authors of work that is presented in the GPCE technical program can obtain even more benefit by presenting their work in a poster as well. The poster session provides them the opportunity to engage in more personal one-on-one discussions.
Suggestions for other key topic areas are also encouraged.
Poster authors are required to attend the scheduled interactive poster session, staying with their poster so that they can discuss their work with conference attendees. Some poster authors also post an informal schedule along with their poster, listing times when they plan to be available for discussion later on during the conference. Others leave sign-up sheets for interested viewers to obtain further information. All posters will have an associated "message board", on which viewers can post comments, ideas, and questions and on which poster authors will be able to post responses.
Posters are advertised in the Final Program, and authors' two-page extended abstracts will appear in the GPCE Conference CD, which will be distributed at to all GPCE'04 attendees. Attendees will be able to learn more about individual posters before or after visiting the exhibit.
For More Information
For additional information, clarification, or questions please feel free to contact the Poster Chair
Vancouver, October 24-28, 2004
co-located with
OOPSLA 2004
and
ISMM 2004
Sponsored by ACM
SIGPLAN,
in cooperation with ACM
SIGSOFT and Microsoft
http://gpce04.gpce.org
Industrial Track Chair
Important Dates
- Practitioner report submission:
- Notification of acceptance:
- Program posted on the conference website:
- Conference:
Overview
Practitioner reports explore how concepts that sound good on paper work on real projects. They are a valuable means of communicating experiences, especially at the "bleeding edge" of technology. Many GPCE attendees want to find out what it is like to adopt new tools and development techniques; use new engineering methods; create domain-specific languages, generators, architectures and components; develop applications using the new technologies, etc. Expectations, beliefs, and hopes can be validated, or dashed, by the experience that is reported. GPCE attendees want objective reports with supporting evidence for any claims made. And they particularly want reports that discuss both benefits and drawbacks of the approaches used.
We seek for reports in two categories:
- Project reports will describe successfully completed projects that applied technologies within the scope of GPCE'04.
- Experience reports will focus on a particular aspect of technology usage and practice, or describe broad project experiences.
The report must contain a take-home-message for your readers; something they can learn and apply to their own work. Plain "how we did it" reports should be avoided.
Presented project and experience reports will take part in the audience vote for the GPCE'04 Best Contribution Awards.
Submission Process
You are invited to submit a four to ten page project report presenting your successful project or experience report describing your experience applying technologies within the scope of GPCE'04. The submission must include a short abstract suitable for inclusion in the Advance Program should it be accepted. If your report is accepted for presentation at GPCE, you will be expected to develop and present a 20 minute talk that will be followed by discussion. The written reports will be published at gpce.org. The submission, including full contact information (name, mailing address, telephone and fax numbers, and electronic mail address), should be submitted as a PDF, OpenOffice, or a Microsoft Word file to the Industrial Track Chair. The report submissions will be reviewed separately from technical paper submissions by a practitioner report committee. The submission should clearly state whether it should be reviewed as a project or experience report.
For More Information
For additional information, clarification, or questions please feel free to contact the Industrial Track Chair.
Vancouver, October 24-28, 2004
co-located with
OOPSLA 2004
and
ISMM 2004
Sponsored by ACM
SIGPLAN,
in cooperation with ACM
SIGSOFT and Microsoft
http://gpce04.gpce.org
Tutorial Chair
Important Dates
- Proposal submission deadline: April 2, 2004
- Notification of acceptance: May 10, 2004
- Camera ready notes: August 6, 2004
- Conference: October 24-28, 2004
- Tutorial day: October 24, 2004
Overview
Proposals for high-quality tutorials in all areas of generative programming and component-based development, from academic research to industrial applications, are solicited. Tutorial levels may be introductory, intermediate, or advanced.
A tutorial's basic purpose is to give a deeper or more covering insight into its area than a conventional lecture would do. That is why it extends over a half or a full day. This gives the speaker better possibilities to structure the tutorial in a proper manner.
The topic of a tutorial can come from a truly broad spectrum. Any interesting theme from or related to the GPCE'04
Call for Papers topic list is welcome, from surveys to experience reports or specialized research topics. However, one should keep in mind that a tutorial can be expected to attract a reasonable number of participants (at least 6 participants). This is most likely the case if the topic is new or relevant to a broad community. If you think that you are highly experienced in a certain area of object-orientation and that others could benefit from sharing this experience with you, you should submit a proposal.
Submission Format
The earlier a proposal arrives, the better the chances to get feedback in order to bring the proposal into a form that is likely to be accepted. Proposals must be submitted electronically via e-mail according to the following template:
- Title
- Select an expressive title that captures the contents of your tutorial well without being too long.
- Remember that the title must be attractive and should make a reader curious.
- In exceptional cases we may re-edit the title in order to make it consistent with other tutorial titles.
- Speaker(s)
- Give the full name and address of the tutorial speaker.
- If there are multiple speakers, give this information for all of them but clearly specify who the contact person is.
- Don't forget to specify the electronic mail address.
- Abstract
- Give a concise description of the contents and goals of your tutorial.
- The abstract will be used for the Advance Program.
- It should not be longer than 150 words.
- If it is longer, be prepared to have it cut or re-edited.
- Outline
- This information will be used by the tutorial committee for reviewing the detailed tutorial contents.
- The outline should be a table of contents of the tutorial, with a few keywords for each section, and with a rough estimate of the time spent on each.
- Duration
- Tutorials can be half-day or full-day.
- Half-day tutorials are preferred. A half-day tutorial should last for 3.5 hours including a half an hour break.
- A full-day tutorial should last for 7 hours including two half an hour and excluding the lunch break.
- Level
- The tutorial level can be introductory (requires almost no experience with object-orientation), intermediate (assumes knowledge of object-oriented concepts but little or no experience with the tutorial's subject), or advanced (assumes several years of practical experience with object-orientation and preferably also some experience with the tutorial's subject).
- Required experience
- Clearly state what knowledge you expect from your participants.
- This information will be included in the Advance Program.
- It should not be longer than 20 words.
- Expected audience
- Who should attend this tutorial?
- How will the participants benefit from attending?
- Speaker's profile
- Describe your affiliation, interests and experience.
- It should be clear from this text that you are the right person to give this tutorial.
- Speaker's profile for the Advance Program
- Provide a short version of the Speaker's profile to be included in the Advance Program.
- It should not be longer than 40 words.
- Tutorial resume
- Has this tutorial been given before?
- How many participants were there?
- If available, please specify the ratings that the participants gave to your tutorial.
- Equipment
- Please specify the equipment you need, e.g., number of slide projectors, video projection facilities, computer tables, power plugs, paper boards, etc.
- Note that we may not be able to provide computers for all the participants.
- Presentations
- Tutorial ma/literials such as slides and handouts should be included if available, but are not required for submission. Providing such materials will show depth and maturity of the tutorial, however, and will be a factor in the selection process. If the tutorial is new, it would still be useful to include a few sample slides that let the committee judge the expected quality of the presentation.
What should a tutorial look like?
If you never presented a tutorial before here are some suggestions that may help you in preparing your presentation.
- Contents
- When preparing the tutorial, keep your audience in mind.
- People don't pay for a tutorial in order to hear things that they already know or that are irrelevant for their work.
- So don't be vague, don't waste time with lengthy introductions, but speak to the point.
- Don't try to impress the audience with the amount of your research, but convey practical knowledge and ideas that the participants will find useful for their own work.
- Whenever possible, use examples and case studies and avoid lengthy abstract passages.
- Also consider demonstrations on video or an overhead panel.
- In order to get an audience as homogeneous as possible, clearly state which knowledge you expect from the participants in the tutorial description.
- Slides and notes
- You will have to prepare tutorial notes for the participants.
- These handouts usually contain copies of the slides that you show.
- Here are a few guidelines for preparing the slides and the handouts.
- Use at least a 14 pt (or better an 18 pt) font on all of your slides.
- A good slide should not just repeat everything you say but summarize your presentation.
- Use short phrases and keywords instead of full sentences.
- People cannot read as fast as you speak. Make heavy use of pictures and examples.
- Consider also using the blackboard for short examples.
- Use colors where they are helpful, but remember that they will not appear in the black and white handouts.
- Don't put too much or too little material on a single slide.
- A good rule of thumb is to spend 3 minutes per slide.
- Don't include slides that you will skip in the presentation; people will find that annoying.
- You will have to deliver the tutorial notes in camera-ready form (see the deadline below).
- We request that you send them as hard copy, so consider the postage delay to meet the deadline.
- To avoid wasting paper, copy two slides on a single page (reduced size). The printed area of such a page must not exceed 27 x 17cm (10.5 x 6.7 inch).
- In addition to the slide copies, also consider providing full-text handouts (papers, summaries, bibliography, etc.). Participants will appreciate that.
- The maximum length of the notes for a half-day tutorial should be 50 pages for slide copies and another 20 pages for full-text material. For full-day tutorials these numbers can be doubled.
- Try to achieve good printing quality.
- We will add an uniform cover page to all tutorial notes.
- Presentation
- The participants expect that your presentation will be much easier to understand than a book about the same subject.
- Thus speak clearly and lively. Try to interact with your audience.
- Encourage them to ask questions.
- A presentation is much more lively if it also includes examples and demonstrations on the blackboard, on video or on an overhead panel.
- Tutorials should be split into sessions of 1.5 hours each with a 0.5 hour coffee break in between.
- Don't overrun your tutorial time. After the tutorial the participants will be asked to assess the tutorial with a questionnaire.
- A good rating will help you when applying for other tutorials in the future.
Submission Process
Please send your tutorial proposals to
tutorials04@gpce.org
Compensation
To be determined...
Related Events
Although GPCE is co-located with OOPSLA, each conference has a separate submission process for tutorials (the co-location should not be understood to mean that these are the same tutorial calls). The OOPSLA call for tutorials can be found at
http://www.oopsla.org/2004/ShowPage.do?id=CallTutorials
For More Information
For additional information, clarification, or questions please feel free to contact the Tutorial Chair (
tutorials04@gpce.org)
Vancouver, October 24-28, 2004
co-located with
OOPSLA 2004
and
ISMM 2004
Sponsored by ACM
SIGPLAN,
in cooperation with ACM
SIGSOFT and Microsoft
http://gpce04.gpce.org
Workshop Chair
Important Dates
Workshop proposals schedule
- Submission deadline for workshop proposals: March 19, 2004
- Notification of workshop acceptance: April 5, 2004
- Workshop program posted on the website: August 31, 2004
This call for participation is for workshop organizers; a later call will occur for workshop attendees.
Workshop attendee schedule (all workshops):
- Calls for Workshop Paper Submissions issued: April 15, 2004
- Workshop paper submission deadline: July 1, 2004
- Workshop papers - notification of acceptance: August 31, 2004
- Workshop papers - final versions posted at the workshop sites: October 20, 2004
- Workshop day: Monday, October 25, 2004
Early conference registration closes on ...
Overview
GPCE workshops provide intensive collaborative environments where generative and component technologists meet to surface, discuss, and solve challenging problems facing the field.
Workshops occur on the day before the conference. To ensure a sufficiently small group for effective interaction, workshop organizers manage attendance based on an objective criterion, typically, a short position paper submitted by potential attendees. Other criteria are permitted as long as they are clearly specified in the workshop's call for participation.
We encourage proposals for innovative, well-focused workshops on a broad spectrum of component engineering and generative programming topics. All topics related to generative programming and component engineering are potential candidates for workshops. Workshops typically fall into the
following categories:
- A workshop may address a specific sub-area of generative and component technology in depth.
- A workshop may cover areas that cross the borders of several sub areas. Workshops that cross the borders of the formal and the applied areas is one example.
- A workshop may focus on the applications and deployment of generative and/or component technology in areas such as telecommunications, mobile computing or real-time systems. Workshops reporting on industrial experiences are particularly welcome.
Workshop topics are by no means limited to the types mentioned above. However, in each case, the proposed area is supposed to have enough impetus to yield new results that can be considered important and worth more detailed investigation.
What should a proposal look like?
Workshop proposals should be sent in ASCII or PDF format to the workshop chair, and they should consist of four pages/parts:
- Cover Page
- Name of the proposed workshop.
- Names and addresses of the organizers.
- Intended number of participants.
- Requested Audio/Video equipment.
- Abstract
- Why it is relevant to GPCE and a short overview of the rationale for the workshop and the major topics. In particular, statements about the review process and ways to ensure creativity during the workshop would be appreciated.
- The abstract should preferably not exceed 200 words.
- Call for Participation
- A preliminary version of the Call for Participation that the organizers must prepare if the workshop is accepted.
- Should provide a brief overview of the proposed workshop including a description of the goals of the workshops and the work practices.
- May repeat some of the statements made on the abstract page, but should be targeted specifically to potential workshop participants.
- Organizers
- Short biography of each organizer.
- References to similar workshops organized at previous conferences, including the number of participants.
- If a workshop is accepted, the organizers will be requested to prepare a WWW page that will contain the latest information about the workshop. The web pages of each workshop will be linked to the GPCE workshop web site.
- Each workshop must have at least two organizers, preferably from different organizations. Preference will be shown to workshops that have more organizers. Workshop organizers and participants have to register for the conference.
Recommendations
- Workshop organizers should in particular take care to foster the creative potential that is tentatively present in a workshop.
- Remember that a workshop is NOT a conference!
- The success of a workshop depends greatly on the results generated on-site.
- A number of interrelated issues should be taken into account in order to provide a good framework for such on-site creativity.
- Time allocation
- During the workshop, enough time should be reserved for collaborative work.
- Such creative sessions should have a precise topic and objective and their results should be written down so that they can be reported later.
Reasonable expectations
- One should not count on people's instantaneous and proactive participation.
- For many reasons, participants tend to prefer a consumer role much to a producer role during a workshop.
- Thus prescreened presentations, even formally reviewed papers, should usually precede any creative sessions.
Task forces
- Large groups tend to behave like an audience, whereas groups of four to eight people are much more likely to interact.
- When planning collaborative sessions, consider having several smaller groups rather than one large group in order to foster the generation of new ideas.
- Presentation selection
- Quality should obviously be the primary criterion for selecting the presentations.
- However, in order for a workshop to be productive, consider also having presentations on some new, controversial topics to spark discussion.
- Participant selection
- Although the number of workshop participants does not need to be restricted to the selected presenters, the overall size of the workshop should remain small enough to foster creativity.
- Usually this means less than 20 participants.
Submission Process
Electronic submission of proposals is required--send to
workshops04@gpce.org. Proposals must be submitted no later than March 19, 2004, BUT EARLIER IS BETTER, as it allows for a more satisfactory coordination between workshop proposals.
Proposal Review and Acceptance
The proposals received will be reviewed by the Workshop Committee to determine a high quality and appropriate mix for the conference.
For More Information
For additional information, clarification, or questions please feel free to contact the Workshop Chair.
Vancouver, October 24-28, 2004
co-located with
OOPSLA 2004
and
ISMM 2004
Sponsored by ACM
SIGPLAN,
in cooperation with ACM
SIGSOFT and Microsoft
http://gpce04.gpce.org